Type-1 codebook construction with multiple aggregation factors

ABSTRACT

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may determine that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor that corresponds to one of a plurality of configured repetition factors configured at the UE. The UE may identify an applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions. The UE may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook populated based at least in part on the applied repetition factor and on whether the one or more downlink transmissions were successfully received and decoded. The UE may transmit to the base station a feedback report that includes the feedback codebook.

CROSS REFERENCE

This application is a continuation of U.S. Non-provisional applicationSer. No. 17/222,672 by FAKOORIAN et al., entitled “TYPE-1 CODEBOOKCONSTRUCTION WITH MULTIPLE AGGREGATION FACTORS” filed Apr. 5, 2021,which claims the benefit of U.S. Provisional Patent Application No.63/006,554 by FAKOORIAN et al., entitled “TYPE-1 CODEBOOK CONSTRUCTIONWITH MULTIPLE AGGREGATION FACTORS,” filed Apr. 7, 2020, assigned to theassignee hereof, and expressly incorporated by reference herein.

FIELD OF TECHNOLOGY

The following relates generally to wireless communications and morespecifically to type-1 codebook construction with multiple aggregationfactors.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal frequency division multiple access (OFDMA), or discreteFourier transform spread orthogonal frequency division multiplexing(DFT-S-OFDM). A wireless multiple-access communications system mayinclude one or more base stations or one or more network access nodes,each simultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support type-1 codebook construction with multipleaggregation factors. Generally, the described techniques provide formore efficient and responsive codebook generation for hybridautomatic-repeat/request acknowledgment (HARQ-ACK) reporting. Forexample, a base station may schedule a user equipment (UE) for downlinktransmission(s), with each downlink transmission have an associatedrepetition factor (e.g., aggregation factor) from a plurality ofrepetition factors configured at the UE (e.g., one, two, four, eight,etc., aggregation factors). However, the base station and UE mayidentify an applied repetition factor that will be applied to feedbackcodebook generation for the downlink transmission(s). Broadly, theapplied repetition factor may be irrespective of the associatedrepetition factor for the configured downlink transmissions (e.g., maybe the same or may be different than the aggregation factor configuredfor the downlink transmission). The base station may transmit thedownlink transmission(s) to the UE, which then generates a feedbackcodebook to report feedback for the downlink transmission(s) to the basestation. The UE may use the applied repetition factor in generating thefeedback codebook, in addition to whether or not the UE was able tosuccessfully receive and decode one or more repetitions of the downlinktransmission. Accordingly, the UE may transmit or otherwise convey afeedback report to the base station that carries or conveys anindication of the feedback codebook.

A method of wireless communication at a UE is described. The method mayinclude determining that a base station has scheduled the UE for one ormore downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a set of configured repetition factors configured at the UE,identifying an applied repetition factor to apply to feedback codebookgeneration for the one or more downlink transmissions, generating afeedback codebook for reporting feedback for the one or more downlinktransmissions, the feedback codebook populated based on the appliedrepetition factor and on whether the one or more downlink transmissionswere successfully received and decoded, and transmitting to the basestation a feedback report that includes the feedback codebook.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to determine that abase station has scheduled the UE for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a set ofconfigured repetition factors configured at the UE, identify an appliedrepetition factor to apply to feedback codebook generation for the oneor more downlink transmissions, generate a feedback codebook forreporting feedback for the one or more downlink transmissions, thefeedback codebook populated based on the applied repetition factor andon whether the one or more downlink transmissions were successfullyreceived and decoded, and transmit to the base station a feedback reportthat includes the feedback codebook.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for determining that a base station hasscheduled the UE for one or more downlink transmissions, each of the oneor more downlink transmissions having an associated repetition factorthat corresponds to one of a set of configured repetition factorsconfigured at the UE, identifying an applied repetition factor to applyto feedback codebook generation for the one or more downlinktransmissions, generating a feedback codebook for reporting feedback forthe one or more downlink transmissions, the feedback codebook populatedbased on the applied repetition factor and on whether the one or moredownlink transmissions were successfully received and decoded, andtransmitting to the base station a feedback report that includes thefeedback codebook.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to determine that a base station has scheduledthe UE for one or more downlink transmissions, each of the one or moredownlink transmissions having an associated repetition factor thatcorresponds to one of a set of configured repetition factors configuredat the UE, identify an applied repetition factor to apply to feedbackcodebook generation for the one or more downlink transmissions, generatea feedback codebook for reporting feedback for the one or more downlinktransmissions, the feedback codebook populated based on the appliedrepetition factor and on whether the one or more downlink transmissionswere successfully received and decoded, and transmit to the base stationa feedback report that includes the feedback codebook.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the appliedrepetition factor based on a maximum number of configured repetitionfactors from the set of configured repetition factors.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the maximumnumber of configured repetition factors without counting configuredrepetition factors corresponding to inactive semi-persistent scheduling(SPS) configurations.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the maximumnumber of configured repetition factors by counting configuredrepetition factors corresponding to both active and inactive SPSconfigurations.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the appliedrepetition factor as one, and generating the feedback codebook based ona last instance of each downlink transmission that was actually receivedand decoded.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining, for eachof the one or more downlink transmissions, that one or more instances ofthe downlink transmission may have been dropped, and generating thefeedback codebook differently for the one or more instances of thedownlink transmission that may have been dropped and for one or moreinstances of the downlink transmission that may be not dropped.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, generating the feedbackcodebook further may include operations, features, means, orinstructions for generating an acknowledgement/negative-acknowledgement(ACK/NACK) indication for each downlink transmission that was actuallyreceived and decoded, and refraining from generating an ACK/NACKindication for each instance of a dropped downlink transmissionopportunity.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the feedback codebook may begenerated without respect to a downlink control information associatedwith the one or more downlink transmissions.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for generating the feedbackcodebook based on evaluating each of the set of reporting offset valueswithin the evaluation window.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving aconfiguration of a plurality of SPS configurations, wherein eachdownlink transmission of the one or more downlink transmissions isassociated with a common SPS configuration or with different SPSconfigurations of the plurality of SPS configurations.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the feedback codebook is atype-1 codebook.

A method of wireless communication at a base station is described. Themethod may include scheduling a UE for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a set ofconfigured repetition factors configured at the UE, identifying anapplied repetition factor for the UE to apply to feedback codebookgeneration for the one or more downlink transmissions, and receiving afeedback report from the UE that includes a feedback codebook, thefeedback codebook generated for reporting feedback for the one or moredownlink transmissions and populated based on the applied repetitionfactor and on whether the one or more downlink transmissions weresuccessfully received and decoded by the UE.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to schedule a UEfor one or more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a set of configured repetition factors configured at the UE,identify an applied repetition factor for the UE to apply to feedbackcodebook generation for the one or more downlink transmissions, andreceive a feedback report from the UE that includes a feedback codebook,the feedback codebook generated for reporting feedback for the one ormore downlink transmissions and populated based on the appliedrepetition factor and on whether the one or more downlink transmissionswere successfully received and decoded by the UE.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for scheduling a UE for oneor more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a set of configured repetition factors configured at the UE,identifying an applied repetition factor for the UE to apply to feedbackcodebook generation for the one or more downlink transmissions, andreceiving a feedback report from the UE that includes a feedbackcodebook, the feedback codebook generated for reporting feedback for theone or more downlink transmissions and populated based on the appliedrepetition factor and on whether the one or more downlink transmissionswere successfully received and decoded by the UE.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to schedule a UE for one or moredownlink transmissions, each of the one or more downlink transmissionshaving an associated repetition factor that corresponds to one of a setof configured repetition factors configured at the UE, identify anapplied repetition factor for the UE to apply to feedback codebookgeneration for the one or more downlink transmissions, and receive afeedback report from the UE that includes a feedback codebook, thefeedback codebook generated for reporting feedback for the one or moredownlink transmissions and populated based on the applied repetitionfactor and on whether the one or more downlink transmissions weresuccessfully received and decoded by the UE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the appliedrepetition factor based on a maximum number of configured repetitionfactors from the set of configured repetition factors.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the maximumnumber of configured repetition factors without counting configuredrepetition factors corresponding to inactive SPS configurations of theUE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the maximumnumber of configured repetition factors by counting configuredrepetition factors corresponding to both active and inactive SPSconfigurations of the UE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying the appliedrepetition factor as one, where the feedback codebook may be generatedbased on a last instance of each downlink transmission that was actuallyreceived and decoded.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for scheduling, based onthe set of configured repetition factors, at least one non-conflictedinstance of the downlink transmission during an evaluation window thatmay be based on a reporting offset value.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining, for eachof the one or more downlink transmissions, that one or more instances ofthe downlink transmission may have been dropped, where the feedbackcodebook may be generated differently for the one or more instances ofthe downlink transmission that may have been dropped and for one or moreinstances of the downlink transmission that may be not dropped.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the feedback codebook may begenerated based on, an ACK/NACK indication may be generated for eachdownlink transmission that was actually received and decoded by the UE,and an ACK/NACK indication may be not generated for each instance of adropped downlink transmission opportunity.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the feedback codebook may begenerated without respect to a downlink control information associatedwith the one or more downlink transmissions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the UE may be configured witha set of reporting offset values for transmitting the feedback report tothe base station, each of the set of reporting offset valuesrepresenting a number of slots after a last nominal downlinktransmission, the set of reporting offset values spanning an evaluationwindow, and the feedback codebook may be generated based on the UEevaluating each of the set of reporting offset values within theevaluation window.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting aconfiguration of a plurality of SPS configurations, wherein eachdownlink transmission of the one or more downlink transmissions isassociated with a common SPS configuration or with different SPSconfigurations of the plurality of SPS configurations.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the feedback codebook is atype-1 codebook.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for wireless communicationsthat supports type-1 codebook construction with multiple aggregationfactors in accordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a feedback configuration that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIG. 3 illustrates an example of a feedback configuration that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIG. 4 illustrates an example of a process that supports type-1 codebookconstruction with multiple aggregation factors in accordance withaspects of the present disclosure.

FIG. 5 illustrates an example of a feedback configuration that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIGS. 6 and 7 show block diagrams of devices that support type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure.

FIG. 8 shows a block diagram of a communications manager that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIG. 9 shows a diagram of a system including a device that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIGS. 10 and 11 show block diagrams of devices that support type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure.

FIG. 12 shows a block diagram of a communications manager that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIG. 13 shows a diagram of a system including a device that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

FIGS. 14 through 18 show flowcharts illustrating methods that supporttype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Wireless communication systems typically utilize hybridautomatic-repeat/request acknowledgment (HARQ-ACK) feedback reporting toconfirm that a device has successfully received and decoded atransmission. The HARQ-ACK feedback report may include a feedbackcodebook (or simply codebook) that includes a series of bits that aregenerated based on the configuration of the transmission. For example, abase station may schedule a user equipment (UE) with a downlinktransmission (e.g., a physical downlink shared channel (PDSCH)transmission) that includes a repetition factor (or aggregation factor)and associated reporting offset value (e.g., K1 value) for the downlinktransmission. The UE may be configured with multiple PDSCH aggregationfactors, e.g., for a dynamic PDSCH and/or for different semi-persistentscheduling (SPS) configurations. When the repetition or aggregationfactor for a downlink transmission is greater than one, the UE mayreport a negative-acknowledgment (NACK) bit for each repetition of thedownlink transmission until the last repetition. For the lastrepetition, the UE determines whether at least one repetition wassuccessfully received and decoded and reports that acknowledgment/NACK(ACK/NACK) bit for the downlink transmission. However, some repetitionsof the downlink transmission may be conflicted out, and thereforeunavailable for transmission to the UE. This may generate confusion andinaccuracies in the codebook that the UE generates provides to the basestation, which may lead to wasted resources for unnecessaryretransmissions and/or a loss of communications between the UE and basestation.

Aspects of the disclosure are initially described in the context ofwireless communication systems. Generally, the described techniquesprovide for more efficient and responsive codebook generation forHARQ-ACK reporting. For example, a base station may schedule a UE fordownlink transmission(s), with each downlink transmission having anassociated repetition factor (e.g., aggregation factor) from a pluralityof repetition factors configured at the UE (e.g., one, two, four, eight,etc., aggregation factors). However, the base station and UE mayidentify an applied repetition factor that will be applied to feedbackcodebook generation for the downlink transmission(s). Broadly, theapplied repetition factor may be irrespective of the associatedrepetition factor for the configured downlink transmissions (e.g., maybe the same or may be different than the aggregation factor configuredfor the downlink transmission). The base station may transmit thedownlink transmission(s) to the UE, which then generates a feedbackcodebook to report feedback for the downlink transmission(s) to the basestation. The UE may use the applied repetition factor in generating thefeedback codebook, in addition to whether or not the UE was able tosuccessfully receive and decode one or more repetitions of the downlinktransmission. Accordingly, the UE may transmit or otherwise convey afeedback report to the base station that carries or conveys anindication of the feedback codebook.

Aspects of the disclosure are further illustrated by and described withreference to apparatus diagrams, system diagrams, and flowcharts thatrelate to type-1 codebook construction with multiple aggregationfactors.

FIG. 1 illustrates an example of a wireless communication system 100that supports type-1 codebook construction with multiple aggregationfactors in accordance with aspects of the present disclosure. Thewireless communication system 100 may include one or more base stations105, one or more UEs 115, and a core network 130. In some examples, thewireless communication system 100 may be a Long Term Evolution (LTE)network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a NewRadio (NR) network. In some examples, the wireless communication system100 may support enhanced broadband communications, ultra-reliable (e.g.,mission critical) communications, low latency communications,communications with low-cost and low-complexity devices, or anycombination thereof.

The base stations 105 may be dispersed throughout a geographic area toform the wireless communication system 100 and may be devices indifferent forms or having different capabilities. The base stations 105and the UEs 115 may wirelessly communicate via one or more communicationlinks 125. Each base station 105 may provide a coverage area 110 overwhich the UEs 115 and the base station 105 may establish one or morecommunication links 125. The coverage area 110 may be an example of ageographic area over which a base station 105 and a UE 115 may supportthe communication of signals according to one or more radio accesstechnologies.

The UEs 115 may be dispersed throughout a coverage area 110 of thewireless communication system 100, and each UE 115 may be stationary, ormobile, or both at different times. The UEs 115 may be devices indifferent forms or having different capabilities. Some example UEs 115are illustrated in FIG. 1 . The UEs 115 described herein may be able tocommunicate with various types of devices, such as other UEs 115, thebase stations 105, or network equipment (e.g., core network nodes, relaydevices, integrated access and backhaul (IAB) nodes, or other networkequipment), as shown in FIG. 1 .

The base stations 105 may communicate with the core network 130, or withone another, or both. For example, the base stations 105 may interfacewith the core network 130 through one or more backhaul links 120 (e.g.,via an S1, N2, N3, or other interface). The base stations 105 maycommunicate with one another over the backhaul links 120 (e.g., via anX2, Xn, or other interface) either directly (e.g., directly between basestations 105), or indirectly (e.g., via core network 130), or both. Insome examples, the backhaul links 120 may be or include one or morewireless links.

One or more of the base stations 105 described herein may include or maybe referred to by a person having ordinary skill in the art as a basetransceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or agiga-NodeB (either of which may be referred to as a gNB), a Home NodeB,a Home eNodeB, or other suitable terminology.

A UE 115 may include or may be referred to as a mobile device, awireless device, a remote device, a handheld device, or a subscriberdevice, or some other suitable terminology, where the “device” may alsobe referred to as a unit, a station, a terminal, or a client, amongother examples. A UE 115 may also include or may be referred to as apersonal electronic device such as a cellular phone, a personal digitalassistant (PDA), a tablet computer, a laptop computer, or a personalcomputer. In some examples, a UE 115 may include or be referred to as awireless local loop (WLL) station, an Internet of Things (IoT) device,an Internet of Everything (IoE) device, or a machine type communications(MTC) device, among other examples, which may be implemented in variousobjects such as appliances, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with varioustypes of devices, such as other UEs 115 that may sometimes act as relaysas well as the base stations 105 and the network equipment includingmacro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations,among other examples, as shown in FIG. 1 .

The UEs 115 and the base stations 105 may wirelessly communicate withone another via one or more communication links 125 over one or morecarriers. The term “carrier” may refer to a set of radio frequencyspectrum resources having a defined physical layer structure forsupporting the communication links 125. For example, a carrier used fora communication link 125 may include a portion of a radio frequencyspectrum band (e.g., a bandwidth part (BWP)) that is operated accordingto one or more physical layer channels for a given radio accesstechnology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layerchannel may carry acquisition signaling (e.g., synchronization signals,system information), control signaling that coordinates operation forthe carrier, user data, or other signaling. The wireless communicationsystem 100 may support communication with a UE 115 using carrieraggregation or multi-carrier operation. A UE 115 may be configured withmultiple downlink component carriers and one or more uplink componentcarriers according to a carrier aggregation configuration. Carrieraggregation may be used with both frequency division duplexing (FDD) andtime division duplexing (TDD) component carriers.

In some examples (e.g., in a carrier aggregation configuration), acarrier may also have acquisition signaling or control signaling thatcoordinates operations for other carriers. A carrier may be associatedwith a frequency channel (e.g., an evolved universal mobiletelecommunication system terrestrial radio access (E-UTRA) absoluteradio frequency channel number (EARFCN)) and may be positioned accordingto a channel raster for discovery by the UEs 115. A carrier may beoperated in a standalone mode where initial acquisition and connectionmay be conducted by the UEs 115 via the carrier, or the carrier may beoperated in a non-standalone mode where a connection is anchored using adifferent carrier (e.g., of the same or a different radio accesstechnology).

The communication links 125 shown in the wireless communication system100 may include uplink transmissions from a UE 115 to a base station105, or downlink transmissions from a base station 105 to a UE 115.Carriers may carry downlink or uplink communications (e.g., in an FDDmode) or may be configured to carry downlink and uplink communications(e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the radiofrequency spectrum, and in some examples the carrier bandwidth may bereferred to as a “system bandwidth” of the carrier or the wirelesscommunication system 100. For example, the carrier bandwidth may be oneof a number of determined bandwidths for carriers of a particular radioaccess technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz(MHz)). Devices of the wireless communication system 100 (e.g., the basestations 105, the UEs 115, or both) may have hardware configurationsthat support communications over a particular carrier bandwidth or maybe configurable to support communications over one of a set of carrierbandwidths. In some examples, the wireless communication system 100 mayinclude base stations 105 or UEs 115 that support simultaneouscommunications via carriers associated with multiple carrier bandwidths.In some examples, each served UE 115 may be configured for operatingover portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiplesubcarriers (e.g., using multi-carrier modulation (MCM) techniques suchas orthogonal frequency division multiplexing (OFDM) or discrete Fouriertransform spread OFDM (DFT-S-OFDM)). In a system employing MCMtechniques, a resource element may consist of one symbol period (e.g., aduration of one modulation symbol) and one subcarrier, where the symbolperiod and subcarrier spacing are inversely related. The number of bitscarried by each resource element may depend on the modulation scheme(e.g., the order of the modulation scheme, the coding rate of themodulation scheme, or both). Thus, the more resource elements that a UE115 receives and the higher the order of the modulation scheme, thehigher the data rate may be for the UE 115. A wireless communicationsresource may refer to a combination of a radio frequency spectrumresource, a time resource, and a spatial resource (e.g., spatial layersor beams), and the use of multiple spatial layers may further increasethe data rate or data integrity for communications with a UE 115.

One or more numerologies for a carrier may be supported, where anumerology may include a subcarrier spacing (Δf) and a cyclic prefix. Acarrier may be divided into one or more BWPs having the same ordifferent numerologies. In some examples, a UE 115 may be configuredwith multiple BWPs. In some examples, a single BWP for a carrier may beactive at a given time and communications for the UE 115 may berestricted to one or more active BWPs.

The time intervals for the base stations 105 or the UEs 115 may beexpressed in multiples of a basic time unit which may, for example,refer to a sampling period of T_(s)=1/(Δf_(max)·N_(f)) seconds, whereΔf_(max) may represent the maximum supported subcarrier spacing, andN_(f) may represent the maximum supported discrete Fourier transform(DFT) size. Time intervals of a communications resource may be organizedaccording to radio frames each having a specified duration (e.g., 10milliseconds (ms)). Each radio frame may be identified by a system framenumber (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes orslots, and each subframe or slot may have the same duration. In someexamples, a frame may be divided (e.g., in the time domain) intosubframes, and each subframe may be further divided into a number ofslots. Alternatively, each frame may include a variable number of slots,and the number of slots may depend on subcarrier spacing. Each slot mayinclude a number of symbol periods (e.g., depending on the length of thecyclic prefix prepended to each symbol period). In some wirelesscommunication systems 100, a slot may further be divided into multiplemini-slots containing one or more symbols. Excluding the cyclic prefix,each symbol period may contain one or more (e.g., N_(f)) samplingperiods. The duration of a symbol period may depend on the subcarrierspacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallestscheduling unit (e.g., in the time domain) of the wireless communicationsystem 100 and may be referred to as a transmission time interval (TTI).In some examples, the TTI duration (e.g., the number of symbol periodsin a TTI) may be variable. Additionally or alternatively, the smallestscheduling unit of the wireless communication system 100 may bedynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using one or more oftime division multiplexing (TDM) techniques, frequency divisionmultiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A controlregion (e.g., a control resource set (CORESET)) for a physical controlchannel may be defined by a number of symbol periods and may extendacross the system bandwidth or a subset of the system bandwidth of thecarrier. One or more control regions (e.g., CORESETs) may be configuredfor a set of the UEs 115. For example, one or more of the UEs 115 maymonitor or search control regions for control information according toone or more search space sets, and each search space set may include oneor multiple control channel candidates in one or more aggregation levelsarranged in a cascaded manner. An aggregation level for a controlchannel candidate may refer to a number of control channel resources(e.g., control channel elements (CCEs)) associated with encodedinformation for a control information format having a given payloadsize. Search space sets may include common search space sets configuredfor sending control information to multiple UEs 115 and UE-specificsearch space sets for sending control information to a specific UE 115.

Each base station 105 may provide communication coverage via one or morecells, for example a macro cell, a small cell, a hot spot, or othertypes of cells, or any combination thereof. The term “cell” may refer toa logical communication entity used for communication with a basestation 105 (e.g., over a carrier) and may be associated with anidentifier for distinguishing neighboring cells (e.g., a physical cellidentifier (PCID), a virtual cell identifier (VCID), or others). In someexamples, a cell may also refer to a geographic coverage area 110 or aportion of a geographic coverage area 110 (e.g., a sector) over whichthe logical communication entity operates. Such cells may range fromsmaller areas (e.g., a structure, a subset of structure) to larger areasdepending on various factors such as the capabilities of the basestation 105. For example, a cell may be or include a building, a subsetof a building, or exterior spaces between or overlapping with geographiccoverage areas 110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by theUEs 115 with service subscriptions with the network provider supportingthe macro cell. A small cell may be associated with a lower-powered basestation 105, as compared with a macro cell, and a small cell may operatein the same or different (e.g., licensed, unlicensed) frequency bands asmacro cells. Small cells may provide unrestricted access to the UEs 115with service subscriptions with the network provider or may providerestricted access to the UEs 115 having an association with the smallcell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115associated with users in a home or office). A base station 105 maysupport one or multiple cells and may also support communications overthe one or more cells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and differentcells may be configured according to different protocol types (e.g.,MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that mayprovide access for different types of devices.

In some examples, a base station 105 may be movable and thereforeprovide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas 110associated with different technologies may overlap, but the differentgeographic coverage areas 110 may be supported by the same base station105. In other examples, the overlapping geographic coverage areas 110associated with different technologies may be supported by differentbase stations 105. The wireless communication system 100 may include,for example, a heterogeneous network in which different types of thebase stations 105 provide coverage for various geographic coverage areas110 using the same or different radio access technologies.

The wireless communication system 100 may support synchronous orasynchronous operation. For synchronous operation, the base stations 105may have similar frame timings, and transmissions from different basestations 105 may be approximately aligned in time. For asynchronousoperation, the base stations 105 may have different frame timings, andtransmissions from different base stations 105 may, in some examples,not be aligned in time. The techniques described herein may be used foreither synchronous or asynchronous operations.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices and may provide for automated communication betweenmachines (e.g., via Machine-to-Machine (M2M) communication). M2Mcommunication or MTC may refer to data communication technologies thatallow devices to communicate with one another or a base station 105without human intervention. In some examples, M2M communication or MTCmay include communications from devices that integrate sensors or metersto measure or capture information and relay such information to acentral server or application program that makes use of the informationor presents the information to humans interacting with the applicationprogram. Some UEs 115 may be designed to collect information or enableautomated behavior of machines or other devices. Examples ofapplications for MTC devices include smart metering, inventorymonitoring, water level monitoring, equipment monitoring, healthcaremonitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging.

Some UEs 115 may be configured to employ operating modes that reducepower consumption, such as half-duplex communications (e.g., a mode thatsupports one-way communication via transmission or reception, but nottransmission and reception simultaneously). In some examples,half-duplex communications may be performed at a reduced peak rate.Other power conservation techniques for the UEs 115 include entering apower saving deep sleep mode when not engaging in active communications,operating over a limited bandwidth (e.g., according to narrowbandcommunications), or a combination of these techniques. For example, someUEs 115 may be configured for operation using a narrowband protocol typethat is associated with a defined portion or range (e.g., set ofsubcarriers or resource blocks (RBs)) within a carrier, within aguard-band of a carrier, or outside of a carrier.

The wireless communication system 100 may be configured to supportultra-reliable communications or low-latency communications, or variouscombinations thereof. For example, the wireless communication system 100may be configured to support ultra-reliable low-latency communications(URLLC) or mission critical communications. The UEs 115 may be designedto support ultra-reliable, low-latency, or critical functions (e.g.,mission critical functions). Ultra-reliable communications may includeprivate communication or group communication and may be supported by oneor more mission critical services such as mission critical push-to-talk(MCPTT), mission critical video (MCVideo), or mission critical data(MCData). Support for mission critical functions may includeprioritization of services, and mission critical services may be usedfor public safety or general commercial applications. The termsultra-reliable, low-latency, mission critical, and ultra-reliablelow-latency may be used interchangeably herein.

In some examples, a UE 115 may also be able to communicate directly withother UEs 115 over a device-to-device (D2D) communication link 135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115utilizing D2D communications may be within the geographic coverage area110 of a base station 105. Other UEs 115 in such a group may be outsidethe geographic coverage area 110 of a base station 105 or be otherwiseunable to receive transmissions from a base station 105. In someexamples, groups of the UEs 115 communicating via D2D communications mayutilize a one-to-many (1:M) system in which each UE 115 transmits toevery other UE 115 in the group. In some examples, a base station 105facilitates the scheduling of resources for D2D communications. In othercases, D2D communications are carried out between the UEs 115 withoutthe involvement of a base station 105.

In some systems, the D2D communication link 135 may be an example of acommunication channel, such as a sidelink communication channel, betweenvehicles (e.g., UEs 115). In some examples, vehicles may communicateusing vehicle-to-everything (V2X) communications, vehicle-to-vehicle(V2V) communications, or some combination of these. A vehicle may signalinformation related to traffic conditions, signal scheduling, weather,safety, emergencies, or any other information relevant to a V2X system.In some examples, vehicles in a V2X system may communicate with roadsideinfrastructure, such as roadside units, or with the network via one ormore network nodes (e.g., base stations 105) using vehicle-to-network(V2N) communications, or with both.

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC) or 5G core (5GC), which may include at leastone control plane entity that manages access and mobility (e.g., amobility management entity (MIME), an access and mobility managementfunction (AMF)) and at least one user plane entity that routes packetsor interconnects to external networks (e.g., a serving gateway (S-GW), aPacket Data Network (PDN) gateway (P-GW), or a user plane function(UPF)). The control plane entity may manage non-access stratum (NAS)functions such as mobility, authentication, and bearer management forthe UEs 115 served by the base stations 105 associated with the corenetwork 130. User IP packets may be transferred through the user planeentity, which may provide IP address allocation as well as otherfunctions. The user plane entity may be connected to the networkoperators IP services 150. The operators IP services 150 may includeaccess to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS),or a Packet-Switched Streaming Service.

Some of the network devices, such as a base station 105, may includesubcomponents such as an access network entity 140, which may be anexample of an access node controller (ANC). Each access network entity140 may communicate with the UEs 115 through one or more other accessnetwork transmission entities 145, which may be referred to as radioheads, smart radio heads, or transmission/reception points (TRPs). Eachaccess network transmission entity 145 may include one or more antennapanels. In some configurations, various functions of each access networkentity 140 or base station 105 may be distributed across various networkdevices (e.g., radio heads and ANCs) or consolidated into a singlenetwork device (e.g., a base station 105).

The wireless communication system 100 may operate using one or morefrequency bands, typically in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band because thewavelengths range from approximately one decimeter to one meter inlength. The UHF waves may be blocked or redirected by buildings andenvironmental features, but the waves may penetrate structuressufficiently for a macro cell to provide service to the UEs 115 locatedindoors. The transmission of UHF waves may be associated with smallerantennas and shorter ranges (e.g., less than 100 kilometers) compared totransmission using the smaller frequencies and longer waves of the highfrequency (HF) or very high frequency (VHF) portion of the spectrumbelow 300 MHz.

The wireless communication system 100 may also operate in a super highfrequency (SHF) region using frequency bands from 3 GHz to 30 GHz, alsoknown as the centimeter band, or in an extremely high frequency (EHF)region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as themillimeter band. In some examples, the wireless communication system 100may support millimeter wave (mmW) communications between the UEs 115 andthe base stations 105, and EHF antennas of the respective devices may besmaller and more closely spaced than UHF antennas. In some examples,this may facilitate use of antenna arrays within a device. Thepropagation of EHF transmissions, however, may be subject to evengreater atmospheric attenuation and shorter range than SHF or UHFtransmissions. The techniques disclosed herein may be employed acrosstransmissions that use one or more different frequency regions, anddesignated use of bands across these frequency regions may differ bycountry or regulating body.

The wireless communication system 100 may utilize both licensed andunlicensed radio frequency spectrum bands. For example, the wirelesscommunication system 100 may employ License Assisted Access (LAA),LTE-Unlicensed (LTE-U) radio access technology, or NR technology in anunlicensed band such as the 5 GHz industrial, scientific, and medical(ISM) band. When operating in unlicensed radio frequency spectrum bands,devices such as the base stations 105 and the UEs 115 may employ carriersensing for collision detection and avoidance. In some examples,operations in unlicensed bands may be based on a carrier aggregationconfiguration in conjunction with component carriers operating in alicensed band (e.g., LAA). Operations in unlicensed spectrum may includedownlink transmissions, uplink transmissions, P2P transmissions, or D2Dtransmissions, among other examples.

A base station 105 or a UE 115 may be equipped with multiple antennas,which may be used to employ techniques such as transmit diversity,receive diversity, multiple-input multiple-output (MIMO) communications,or beamforming. The antennas of a base station 105 or a UE 115 may belocated within one or more antenna arrays or antenna panels, which maysupport MIMO operations or transmit or receive beamforming. For example,one or more base station antennas or antenna arrays may be co-located atan antenna assembly, such as an antenna tower. In some examples,antennas or antenna arrays associated with a base station 105 may belocated in diverse geographic locations. A base station 105 may have anantenna array with a number of rows and columns of antenna ports thatthe base station 105 may use to support beamforming of communicationswith a UE 115. Likewise, a UE 115 may have one or more antenna arraysthat may support various MIMO or beamforming operations. Additionally oralternatively, an antenna panel may support radio frequency beamformingfor a signal transmitted via an antenna port.

The base stations 105 or the UEs 115 may use MIMO communications toexploit multipath signal propagation and increase the spectralefficiency by transmitting or receiving multiple signals via differentspatial layers. Such techniques may be referred to as spatialmultiplexing. The multiple signals may, for example, be transmitted bythe transmitting device via different antennas or different combinationsof antennas. Likewise, the multiple signals may be received by thereceiving device via different antennas or different combinations ofantennas. Each of the multiple signals may be referred to as a separatespatial stream and may carry bits associated with the same data stream(e.g., the same codeword) or different data streams (e.g., differentcodewords). Different spatial layers may be associated with differentantenna ports used for channel measurement and reporting. MIMOtechniques include single-user MIMO (SU-MIMO), where multiple spatiallayers are transmitted to the same receiving device, and multiple-userMIMO (MU-MIMO), where multiple spatial layers are transmitted tomultiple devices.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a base station 105, a UE 115) to shape or steeran antenna beam (e.g., a transmit beam, a receive beam) along a spatialpath between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that some signals propagatingat particular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying amplitude offsets, phase offsets, or both to signals carriedvia the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

A base station 105 or a UE 115 may use beam sweeping techniques as partof beam forming operations. For example, a base station 105 may usemultiple antennas or antenna arrays (e.g., antenna panels) to conductbeamforming operations for directional communications with a UE 115.Some signals (e.g., synchronization signals, reference signals, beamselection signals, or other control signals) may be transmitted by abase station 105 multiple times in different directions. For example,the base station 105 may transmit a signal according to differentbeamforming weight sets associated with different directions oftransmission. Transmissions in different beam directions may be used toidentify (e.g., by a transmitting device, such as a base station 105, orby a receiving device, such as a UE 115) a beam direction for latertransmission or reception by the base station 105.

Some signals, such as data signals associated with a particularreceiving device, may be transmitted by a base station 105 in a singlebeam direction (e.g., a direction associated with the receiving device,such as a UE 115). In some examples, the beam direction associated withtransmissions along a single beam direction may be determined based on asignal that was transmitted in one or more beam directions. For example,a UE 115 may receive one or more of the signals transmitted by the basestation 105 in different directions and may report to the base station105 an indication of the signal that the UE 115 received with a highestsignal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a base station 105or a UE 115) may be performed using multiple beam directions, and thedevice may use a combination of digital precoding or radio frequencybeamforming to generate a combined beam for transmission (e.g., from abase station 105 to a UE 115). The UE 115 may report feedback thatindicates precoding weights for one or more beam directions, and thefeedback may correspond to a configured number of beams across a systembandwidth or one or more sub-bands. The base station 105 may transmit areference signal (e.g., a cell-specific reference signal (CRS), achannel state information reference signal (CSI-RS)), which may beprecoded or unprecoded. The UE 115 may provide feedback for beamselection, which may be a precoding matrix indicator (PMI) orcodebook-based feedback (e.g., a multi-panel type codebook, a linearcombination type codebook, a port selection type codebook). Althoughthese techniques are described with reference to signals transmitted inone or more directions by a base station 105, a UE 115 may employsimilar techniques for transmitting signals multiple times in differentdirections (e.g., for identifying a beam direction for subsequenttransmission or reception by the UE 115) or for transmitting a signal ina single direction (e.g., for transmitting data to a receiving device).

A receiving device (e.g., a UE 115) may try multiple receiveconfigurations (e.g., directional listening) when receiving varioussignals from the base station 105, such as synchronization signals,reference signals, beam selection signals, or other control signals. Forexample, a receiving device may try multiple receive directions byreceiving via different antenna subarrays, by processing receivedsignals according to different antenna subarrays, by receiving accordingto different receive beamforming weight sets (e.g., differentdirectional listening weight sets) applied to signals received atmultiple antenna elements of an antenna array, or by processing receivedsignals according to different receive beamforming weight sets appliedto signals received at multiple antenna elements of an antenna array,any of which may be referred to as “listening” according to differentreceive configurations or receive directions. In some examples, areceiving device may use a single receive configuration to receive alonga single beam direction (e.g., when receiving a data signal). The singlereceive configuration may be aligned in a beam direction determinedbased on listening according to different receive configurationdirections (e.g., a beam direction determined to have a highest signalstrength, highest signal-to-noise ratio (SNR), or otherwise acceptablesignal quality based on listening according to multiple beamdirections).

The wireless communication system 100 may be a packet-based network thatoperates according to a layered protocol stack. In the user plane,communications at the bearer or Packet Data Convergence Protocol (PDCP)layer may be IP-based. A Radio Link Control (RLC) layer may performpacket segmentation and reassembly to communicate over logical channels.A Medium Access Control (MAC) layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use error detection techniques, error correction techniques, orboth to support retransmissions at the MAC layer to improve linkefficiency. In the control plane, the Radio Resource Control (RRC)protocol layer may provide establishment, configuration, and maintenanceof an RRC connection between a UE 115 and a base station 105 or a corenetwork 130 supporting radio bearers for user plane data. At thephysical layer, transport channels may be mapped to physical channels.

The UEs 115 and the base stations 105 may support retransmissions ofdata to increase the likelihood that data is received successfully.Hybrid automatic repeat request (HARQ) feedback is one technique forincreasing the likelihood that data is received correctly over acommunication link 125. HARQ may include a combination of errordetection (e.g., using a cyclic redundancy check (CRC)), forward errorcorrection (FEC), and retransmission (e.g., automatic repeat request(ARQ)). HARQ may improve throughput at the MAC layer in poor radioconditions (e.g., low signal-to-noise conditions). In some examples, adevice may support same-slot HARQ feedback, where the device may provideHARQ feedback in a specific slot for data received in a previous symbolin the slot. In other cases, the device may provide HARQ feedback in asubsequent slot, or according to some other time interval.

A UE 115 may determine that a base station 105 has scheduled the UE 115for one or more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a plurality of configured repetition factors configured at the UE115. The UE 115 may identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions.The UE 115 may generate a feedback codebook for reporting feedback forthe one or more downlink transmissions, the feedback codebook populatedbased at least in part on the applied repetition factor and on whetherthe one or more downlink transmissions were successfully received anddecoded. The UE 115 may transmit to the base station 105 a feedbackreport that includes the feedback codebook.

A base station 105 may schedule a UE 115 for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a plurality ofconfigured repetition factors configured at the UE 115. The basestation1 105 may identify an applied repetition factor for the UE 115 toapply to feedback codebook generation for the one or more downlinktransmissions. The base station 105 may receive a feedback report fromthe UE 115 that includes a feedback codebook, the feedback codebookgenerated for reporting feedback for the one or more downlinktransmissions and populated based at least in part on the appliedrepetition factor and on whether the one or more downlink transmissionswere successfully received and decoded by the UE 115.

FIG. 2 illustrates an example of a feedback configuration 200 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. In some examples,feedback configuration 200 may implement aspects of wirelesscommunication system 100. Aspects of feedback configuration 200 may beimplemented by a base station and/or UE, which may be examples of thecorresponding devices described herein.

Broadly, feedback configuration 200 spans a plurality of slots 205, withfive slots 205 being shown by way of example only. Slots 205 may beconfigured with one or more PDSCH occasions 210, a first downlinktransmission 215 (e.g., PDSCH #1), a second downlink transmission 220(e.g., PDSCH #2), and a physical uplink control channel (PUCCH) 225(e.g., a feedback reporting occasion where the UE transmits a feedbackreport to a base station for the downlink transmissions).

In some wireless communication systems, a UE typically reports HARQ-ACKinformation (e.g., a feedback report) for a PDSCH reception (e.g.,downlink transmission) from slot n−N_(PDSCH) ^(repeat)+1 to slot n in aHARQ-ACK codebook that the UE includes in a PUCCH or physical uplinkshared channel (PUSCH) transmission in slot n+k. N_(PDSCH) ^(repeat) maybe a value of the PDSCH aggregation or repetition factor(pdsch-AggregationFactor) if the UE is provided or otherwise configuredwith a PDSCH aggregation factor. Otherwise, N_(PDSCH) ^(repeat) may beassumed to be one. k may be a number of slots indicated by thePDSCH-to-HARQ feedback timing indicator (e.g., the offset reporting slotindicated by a K or K1 value) in a corresponding downlink controlinformation (DCI) format, or provided by dl-DatatoUL-ACK if thePDSCH-to-HARQ feedback timing indicator field is not present in the DCIformat. If the UE reports HARQ-ACK information for the PDSCH receptionin the slot other than slot n, the UE sets a value for eachcorresponding HARQ-ACK information bit to NACK or N. If the UE isprovided with tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated and none of the repetitions arereceived due to an uplink/downlink interaction/conflict, then noACK/NACK bit is generated in the codebook for the associated PDSCH withN_(PDSCH) ^(repeat) repetitions.

In some wireless communication systems, the UE may be configured withmultiple SPS configurations. For example, these wireless communicationsystems may utilize a configuration of a PDSCH aggregation factor(pdsch-AggregationFactor) per downlink SPS configuration, withaggregation factor values ranging from {1,2,4,8} (e.g., aggregation orrepetition factors of one, two, four, or eight). For PDSCH scheduledwithout a corresponding PDCCH transmission (e.g., without DCI) usingsps-Config and activated by the DCI format 1_1 or 1_2, or a PDSCHscheduled by the DCI format 1_1 or 1_2 in PDCCH with a cyclic redundancycheck (CRC) scrambled with a configured scheduling radio networktemporary identifier (CS-RNTI) with a new data indicator (NDI) set tozero, the PDSCH aggregation factor signaled in sps-Config is applied, ifconfigured. Otherwise, the PDSCH aggregation factor signaled inpdsch-Config is applied. For PDSCH scheduled by the DCI format 1_1 or1_2 in PDCCH with the CRC scrambled with CS-RNTI and the NDI set to one,the PDSCH aggregation factor signaled in pdsch-Config is applied.

Accordingly, the UE may be configured with multiple downlinktransmission aggregation factors (e.g., pdsch-AggregationFactor), e.g.,for dynamic PDSCH in pdsch-Config and/or for different SPSconfigurations in sps-Config, and these configurations may havedifferent values of aggregation or repetition factors (e.g.,pdsch-AggregationFactor). When multiple aggregation or repetitionfactors are configured, this raises the question of what should be setfor N_(PDSCH) ^(repeat) for the purpose of determining when to send atype-1 HARQ-ACK codebook (e.g., in which sub-slot or slot the HARQ-ACKcodebook, such as a feedback report, is sent over PUCCH or PUSCH) and/orhow to construct the type-1 HARQ-ACK codebook (e.g., that includes thecodebook size and ACK/NACK bit location within the codebook).

In such wireless communication systems, a type-1 codebook constructionhas a size overhead issue when the PDSCH aggregation factor is greaterthan one and a PDSCH occasion is dropped (e.g., due to a downlink/uplinkinteraction or conflict). That is, the UE may be configured with onlyone PDSCH aggregation factor that is set to two (e.g., two repetitionseach for the first downlink transmission 215 and the second downlinktransmission 220 in the example illustrated in feedback configuration200). The configured set of K1 values (illustrated as K) may be {1,2,4,8}. In slot n (e.g., slot 205-d), the second repetition of the seconddownlink transmission 220 is dropped due to a conflict with an uplinksymbol/signal. Additionally, both PDSCH occasions of slot n−2 (e.g.,slot 205-b) overlap with uplink symbols or signals, and therefore thefirst repetition of the first downlink transmission 215 is dropped. Thetime domain resource allocation (TDRA) table may have only two,non-overlapping start and length indicator value (SLIV) rows for a PDSCHas shown in the “old” codebook (e.g., N,N for slot 205-b, A/N,N for slot205-c, and N,A/N for slot 205-d). However, the codeword generated usingthe conventional techniques (e.g., the “old” codebook) includesexcessive bits, which increases the size and/or complexity of thecodebook. This may also create confusion between the base station and UEwith respect to how the codebook is generated, and can therefore be readby the base station. However, aspects of the described techniques enablethe dropped PDSCH occasions (e.g., occasions in which a downlinktransmission could be or is scheduled for a UE) to be removed from atype-1 codebook.

Accordingly, aspects of the described techniques provide for a basestation to schedule a UE for one or more downlink transmissions (e.g.,the first downlink transmission 215 and the second downlink transmission220 by way of example only). Each downlink transmission may have anassociated repetition factor (e.g., an aggregation factor that is twofor both downlink transmissions in this example) that corresponds to oneof a plurality of repetition factors configured at the UE (e.g.,{1,2,4,8}). But the base station and UE may identify an appliedrepetition factor (aggregation factor) to be applied to feedbackcodebook generation for the scheduled downlink transmissions instead ofthe associated repetition or aggregation factor.

The base station may transmit the downlink transmissions to the UEaccording to the configurations. For example, slot n−3 (e.g., slot205-a) is scheduled with two PDSCH occasions 210. Broadly, PDSCHoccasions 210 generally refer to occasions (in the form of resources) inwhich a downlink transmission can be scheduled for the UE. In feedbackconfiguration 200, the PDSCH occasions 210 shown are resources where adownlink transmission can be scheduled, but are not scheduled. However,each of the downlink transmissions occurs during a PDSCH occasion. Infeedback configuration 200, the actually scheduled transmissions areindicated as a PDSCH transmission, while unused transmission resourcesor occasions are referred to as PDSCH occasions 210. Each of the slotson which PDSCH may be received is illustrated as having the same PDSCHoccasions. As discussed, portions of slot n−2 (e.g., slot 205-b) havebeen configured as uplink portions that overlap with both PDSCHoccasions, and therefore any PDSCH occurring within that slot (e.g.,whether the PDSCH occasion 210 or a first repetition of the firstdownlink transmission 215) are dropped. During slot n−1 (e.g., slot205-c), the base station may transmit the second repetition of the firstdownlink transmission 215 (having a reporting offset of K or K1=2) andthe first repetition of the second downlink transmission 220 (having areporting offset of K or K1=1). As also discussed, during slot n (e.g.,slot 205-d), the second repetition of the second downlink transmission220 is conflicted out, and therefore not transmitted or dropped.

Accordingly, the UE may generate a feedback codebook for reportingfeedback for the scheduled downlink transmissions that is populatedbased at least in part on the applied repetition factor and on whetherthe scheduled downlink transmissions were successfully received anddecoded by the UE. That is, the UE may utilize the applied repetitionfactor rather than the repetition factor associated with the downlinktransmission(s) configured by the base station. Various alternatives maybe utilized with respect to identifying and applying the appliedrepetition factor.

One alternative may include identifying the applied repetition factorbased on a maximum number of configured repetition factors from theconfigured repetition factors of the UE (e.g., the maximum across allPDSCH aggregation factors, or pdsch-AggregationFactor, configurations).For example, the UE and base station may both identify the maximumnumber of configured repetition factors without counting or otherwiseconsidering the configured repetition factors corresponding to inactiveSPS configuration(s) (e.g., the PDSCH aggregation factors do not includeinactive SPS configurations, when configured for the UE). In anotherexample, the base station and UE may identify the maximum number ofconfigured repetition factor by counting the configured repetitionfactors corresponding to both active and inactive SPS configurations(e.g., the PDSCH aggregation factor, or pdsch-AggregationFactor,configurations that includes both active and inactive SPSconfigurations, when configured for the UE). In a given slot 205, theACK/NACK bit position in a type-1 codebook corresponding to a PDSCH fromthe TDRA table is dropped only if that PDSCH is dropped in that slot 205and all (e.g., max_pdsch-AggregationFactor)-1 slots 205. The codebooksize would have a larger overhead when the PDSCH within a K−1 window isdropped (e.g., as illustrated in the “old” codebook).

One alternative may include identifying the applied repetition factor asone. In this instance, the UE may generate the feedback codebook basedon the last instance of each downlink transmission that was actuallyreceived and decoded. For example, N_(PDSCH) ^(repeat) may always beconsidered as one and the ACK/NACK bit position for each PDSCH withrepetitions may be tied with the last actual PDSCH reception. This mayresult in the UE generating the “new” codebook illustrated in feedbackconfiguration 200. As can be seen, this approach reduces the size of thecodebook that the UE generates and transmits to the base station byhalf. That is, this reduces the codebook size when some PDSCH occasionsare dropped and the PDSCH aggregation factor is greater than one, witheven increased benefits when the PDSCH aggregation factor is large.

Accordingly, the UE and base station may determine that instance(s) ofthe downlink transmissions have been dropped. Accordingly, the UE maygenerate the feedback codebook differently for the dropped downlinktransmissions than for the non-dropped downlink transmissions. Forexample, the UE may generate an ACK/NACK indication (e.g., ACK/NACK bit)for each downlink transmission that was actually received and decoded,but not generate an ACK/NACK indication breach instance of a droppeddownlink transmission opportunity.

In some aspects, the feedback codebook may be generated without respectto a DCI associated with the downlink transmissions (e.g., may be basedon SPS configurations). For example, the UE may generate a type-1feedback codebook based on the SPS configuration provided by the basestation.

During slot n+1 (e.g., slot 205-e), the UE may transmit or otherwiseconvey an indication of a feedback report (e.g., PUCCH 225) to the basestation that includes the feedback codebook (e.g., the “new” codebook)generated in accordance with the described techniques. As discussed,these techniques may improve the codebook generation by the UE, reducethe overall size of the codebook to minimize overhead, and moreaccurately ensure consistency between the codebook the UE generates andthe codebook that the base station expects to receive.

FIG. 3 illustrates an example of a feedback configuration 300 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. In some examples,feedback configuration 300 may implement aspects of wirelesscommunication system 100 and/or feedback configuration 200. Aspects offeedback configuration 300 may be implemented by a base station and/orUE, which may be examples of the corresponding devices described herein.

Broadly, feedback configuration 300 spans a plurality of slots 305, withfive slots 305 being shown by way of example only. Slots 305 may beconfigured with one or more PDSCH occasions 310, a first downlinktransmission 315 (e.g., PDSCH #1), a second downlink transmission 320(e.g., PDSCH #2), and a PUCCH 325 (e.g., a feedback reporting occasionwhere the UE transmits a feedback report to the base station for thedownlink transmissions).

As discussed above, a base station may schedule the UE for one or moredownlink transmissions (e.g., the first downlink transmission 315 andthe second downlink transmission 320 by way of example only). Eachdownlink transmission may have an associated repetition factor (e.g., anaggregation factor that is two for the first downlink transmission 315and four for the second downlink transmission 320 in this example) thatcorresponds to one of a plurality of repetition factors configured atthe UE (e.g., {1,2,4,8}). But the base station and UE may identify anapplied repetition factor (aggregation factor) to be applied to feedbackcodebook generation for the scheduled downlink transmissions instead ofthe associated repetition or aggregation factor. For example, theapplied repetition factor may be one, as discussed in relation to FIG. 2.

The base station may transmit the downlink transmissions 315, 320 to theUE according to the configurations. For example, slot n−3 (e.g., slot305-a) is scheduled for transmission of a first repetition of both thefirst downlink transmission 315 and the second downlink transmission320. Slot n−2 (e.g., slot 305-b) has been configured to include uplinkportions that overlap with the scheduled repetitions of both downlinktransmissions 315, 320, and therefore any PDSCH(s) occurring within thatslot (e.g., both of the second repetitions of the first downlinktransmission 315 and second downlink transmission 320) are dropped.During slot n−1 (e.g., slot 305-c), the base station may transmit thethird repetition of the second downlink transmission 320, while thePDSCH occasion 310 is unused. During slot n (e.g., slot 305-d), thePDSCH occasion 310 is again unused and the fourth repetition of thesecond downlink transmission 320 is dropped (e.g., conflicted out due toa designated uplink portion of slot n). The first downlink transmission315 has a corresponding reporting offset of K or K1=3 and the seconddownlink transmission 320 has a corresponding reporting offset of K orK1=1.

Accordingly, the UE may generate a feedback codebook for reportingfeedback for the scheduled downlink transmissions that is populatedbased at least in part on the applied repetition factor and on whetherthe scheduled downlink transmissions were successfully received anddecoded by the UE. That is, the UE may utilize the applied repetitionfactor rather than the repetition factor associated with the downlinktransmission(s) configured by the base station.

In the example of FIG. 3 , if the applied repetition factor is one, andif the UE is configured with a K1 window of {1, 2, 3}, the ACK/NACK bitfor the downlink transmission 315 will not be captured in the feedbackcodebook. If the applied repletion factor is one, the UE will considerslots n, n−1, and n−2 (corresponding to the K1 window) when populatingthe feedback codebook. Using the process outlined with respect to FIG. 2, nothing would be included in the codebook corresponding to slot n−2.In slot n−1, a NACK will be included to correspond to unused PDSCHoccasion 310, and an ACK/NACK will be included to correspond to thethird repetition of downlink transmission 320. In slot n, only a NACKwill be included, corresponding to the unused PDSCH occasion 310. Assuch, while the feedback codebook is still reduced, the codebook lacksany reporting for downlink transmission 315. A scheduling rule may beused to avoid this scenario.

In feedback configuration 300, the scheduling rule may include that theUE may not expect to be configured with a set of K−1 values that, for agiven PDSCH with a PDSCH aggregation factor of greater than one, none ofthe actual PDSCH reception lie within the K1 window. That is, the UE mayexpect to be configured such that at least one reception of a PDSCH lieswithin the K1 window. For example, the UE may be configured with theplurality of reporting offset values for transmitting the feedbackreport to the base station, where each of the reporting offset valuesrepresent a number of slots after a last nominal downlink transmission.The reporting offset values may span an evaluation window and thefeedback codebook may be generated based on the UE evaluating each ofthe plurality of reporting offset values within the evaluation window.The UE may generate the feedback codebook based on this technique.

During slot n+1 (e.g., slot 305-e), the UE may transmit or otherwiseconvey an indication of a feedback report (e.g., PUCCH 325) to the basestation that includes the feedback codebook generated in accordance withthe described techniques. As discussed, these techniques may improve thecodebook generation by the UE, reduce the overall size of the codebookto minimize overhead, and more accurately ensure consistency between thecodebook the UE generates and the codebook that the base station expectsto receive.

FIG. 4 illustrates an example of a process 400 that supports type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure. In some examples, process 400may implement aspects of wireless communication system 100 and/orfeedback configurations 200 and/or 300. Aspects of process 400 may beimplemented by UE 405 and/or base station 410, which may be examples ofthe corresponding devices described herein.

At 415, base station 410 may schedule UE 405 for one or more downlinktransmissions (e.g., PDSCH transmissions), with each downlinktransmission having an associated repetition factor (e.g., PDSCHaggregation factor) corresponding to one of the plurality of repetitionfactors configured at UE 405 by base station 410.

At 420, UE 405 may identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions.Similarly and at 425, the base station may also identify an appliedrepetition factor for UE 405 to apply to feedback codebook generationfor the one or more downlink transmissions. For example, base station410 may transmit a configuration signal (e.g., in RRC configurationsignaling) to UE 405 identifying the applied repetition factor to beutilized for feedback codebook generation. In another example, basestation 410 may configure SPS configuration(s) for UE 405, which mayimplicitly indicate that the applied petition factor is to be used.

Accordingly and at 430, UE 405 may generate a feedback codebook forreporting feedback for the downlink transmissions. The feedback codebookmay be populated based on the applied repetition factor and on whetherone or more of the downlink transmissions were successfully received anddecoded by UE 405. In some aspects, the feedback codebook may begenerated without respect to the DCI associated with the downlinktransmissions.

For example, UE 405 may identify the applied repetition factor based ona maximum number of configured repetition factors from the plurality ofconfigured repetition factors. For example, UE 405 may identify themaximum number of configured repetition factors without countinginactive SPS configurations. In another example, UE 405 may identify themaximum number of configured repetition factors by counting both activeand inactive SPS configurations. In some aspects, this may include UE405 identifying the applied repetition factor as one. Accordingly, UE405 may generate feedback codebook based on a last instance of eachdownlink transmission that was actually successfully received anddecoded.

In some aspects, this may include UE 405 determining that one or moreinstances of the downlink transmissions have been dropped. Accordingly,UE 405 may generate the feedback codebook differently for the droppeddownlink transmissions than for the non-dropped (e.g., actuallytransmitted) downlink transmissions. For example, UE 405 may generate anACK/NACK indication for each downlink transmission that was actuallyreceived and decoded, but refrain from generating an ACK/NACK indicationfor a dropped downlink transmission.

In some aspects, this may include UE 405 being configured with theplurality of reporting offset values (e.g., K or K−1 values) fortransmitting the feedback report to the base station. Each reportingoffset value may represent a number of slots after a last nominaldownlink transmission, and the reporting offset values may span anevaluation window (e.g., a K1 window). UE 405 may generate the feedbackcodebook based on an evaluation of each reporting offset value withinthe evaluation window.

Accordingly and at 435, UE 405 may transmit (and base station 410 mayreceive) a feedback report that includes the feedback codebook generatedin accordance with the described techniques. The feedback report may betransmitted by PUCCH and/or PUSCH.

FIG. 5 illustrates an example of a feedback configuration 500 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. In some examples,feedback configuration 500 may implement aspects of wirelesscommunication system 100, feedback configuration 200 and/or 300, and/orprocess 400. Aspects of feedback configuration 500 may be implemented bya base station and/or UE, which may be examples of the correspondingdevices described herein.

Broadly, feedback configuration 500 spans a plurality of slots 505, withfive slots 505 being shown by way of example only. Slots 505 may beconfigured with a first downlink transmission 515 (e.g., PDSCH #1), asecond downlink transmission 520 (e.g., PDSCH #2), and a PUCCH 525(e.g., a feedback reporting occasion where the UE transmits a feedbackreport to a base station for the downlink transmissions).

As discussed above, a base station may schedule the UE for one or moredownlink transmissions (e.g., the first downlink transmission 515 andthe second downlink transmission 520 by way of example only). Eachdownlink transmission may have an associated repetition factor (e.g., anaggregation factor that is two for the first downlink transmission 515and three for the second downlink transmission 520 in this example) thatcorresponds to one of a plurality of repetition factors configured atthe UE (e.g., {1,2,4,8}). But the base station and UE may identify anapplied repetition factor (aggregation factor) to be applied to feedbackcodebook generation for the scheduled downlink transmissions instead ofthe associated repetition or aggregation factor.

The base station may transmit the downlink transmissions to the UEaccording to the configurations. For example, slot n−3 (e.g., slot505-a) is scheduled for transmission of a first repetition of the seconddownlink transmission 520. Slot n−2 (e.g., slot 505-b) is scheduled fortransmission of a first repetition of the first downlink transmission515 and second repetition of the second downlink transmission 520. Slotn−1 (e.g., slot 505-c) is scheduled for transmission of a secondrepetition of the first downlink transmission 515 and third repetitionof the second downlink transmission 520. During slot n (e.g., slot505-d), the second downlink transmission 520 is dropped (e.g.,conflicted out). The first downlink transmission 515 has a correspondingreporting offset of K or K1=2 and the second downlink transmission 520has a corresponding reporting offset of K or K1=1.

Accordingly, the UE may generate a feedback codebook for reportingfeedback for the scheduled downlink transmissions that is populatedbased at least in part on the applied repetition factor and on whetherthe scheduled downlink transmissions were successfully received anddecoded by the UE. That is, the UE may utilize the applied repetitionfactor rather than the repetition factor associated with the downlinktransmission(s) configured by the base station.

In the example illustrated in feedback configuration 500, regardless ofhow many PDSCH aggregation factors are configured, the UE may reportHARQ-ACK information for a PDSCH with N_(PDSCH)^(repeat)=pdsch−AggregationFactor repetitions, from slot n−N_(PDSCH)^(repeat)+1 to slot n, when in the HARQ-ACK codebook that the UEincludes in a PUCCH or PUSCH transmission in slot n+k, where k isindicted in the DCI. N_(PDSCH) ^(repeat) may be defined per PDSCH, e.g.,pdsch-AggregationFactor can be two or four, for example, forrespectively configured downlink grant and SPS configured downlinktransmissions.

Accordingly, during slot n+1 (e.g., slot 505-e) the UE may transmit (andbase station may receive) a feedback report (e.g., PUCCH 525) thatincludes the feedback codebook generated in accordance with thedescribed techniques. The feedback report may be transmitted by PUCCH525 and/or PUSCH.

FIG. 6 shows a block diagram 600 of a device 605 that supports type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure. The device 605 may be an exampleof aspects of a UE 115 as described herein. The device 605 may include areceiver 610, a communications manager 615, and a transmitter 620. Thedevice 605 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

The receiver 610 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to type-1codebook construction with multiple aggregation factors, etc.).Information may be passed on to other components of the device 605. Thereceiver 610 may be an example of aspects of the transceiver 920described with reference to FIG. 9 . The receiver 610 may utilize asingle antenna or a set of antennas.

The communications manager 615 may determine that a base station hasscheduled the UE for one or more downlink transmissions, each of the oneor more downlink transmissions having an associated repetition factorthat corresponds to one of a set of configured repetition factorsconfigured at the UE, identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions,generate a feedback codebook for reporting feedback for the one or moredownlink transmissions, the feedback codebook populated based on theapplied repetition factor and on whether the one or more downlinktransmissions were successfully received and decoded, and transmit tothe base station a feedback report that includes the feedback codebook.The communications manager 615 may be an example of aspects of thecommunications manager 910 described herein.

The communications manager 615, or its sub-components, may beimplemented in hardware, code (e.g., software or firmware) executed by aprocessor, or any combination thereof. If implemented in code executedby a processor, the functions of the communications manager 615, or itssub-components may be executed by a general-purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a field-programmable gate array (FPGA), or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed in the present disclosure.

The communications manager 615, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationsmanager 615, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communications manager 615, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 620 may transmit signals generated by other componentsof the device 605. In some examples, the transmitter 620 may becollocated with a receiver 610 in a transceiver module. For example, thetransmitter 620 may be an example of aspects of the transceiver 920described with reference to FIG. 9 . The transmitter 620 may utilize asingle antenna or a set of antennas.

FIG. 7 shows a block diagram 700 of a device 705 that supports type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure. The device 705 may be an exampleof aspects of a device 605, or a UE 115 as described herein. The device705 may include a receiver 710, a communications manager 715, and atransmitter 740. The device 705 may also include a processor. Each ofthese components may be in communication with one another (e.g., via oneor more buses).

The receiver 710 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to type-1codebook construction with multiple aggregation factors, etc.).Information may be passed on to other components of the device 705. Thereceiver 710 may be an example of aspects of the transceiver 920described with reference to FIG. 9 . The receiver 710 may utilize asingle antenna or a set of antennas.

The communications manager 715 may be an example of aspects of thecommunications manager 615 as described herein. The communicationsmanager 715 may include a scheduling manager 720, an applied repetitionfactor manager 725, a feedback codebook manager 730, and a feedbackreport manager 735. The communications manager 715 may be an example ofaspects of the communications manager 910 described herein.

The scheduling manager 720 may determine that a base station hasscheduled the UE for one or more downlink transmissions, each of the oneor more downlink transmissions having an associated repetition factorthat corresponds to one of a set of configured repetition factorsconfigured at the UE.

The applied repetition factor manager 725 may identify an appliedrepetition factor to apply to feedback codebook generation for the oneor more downlink transmissions.

The feedback codebook manager 730 may generate a feedback codebook forreporting feedback for the one or more downlink transmissions, thefeedback codebook populated based on the applied repetition factor andon whether the one or more downlink transmissions were successfullyreceived and decoded.

The feedback report manager 735 may transmit to the base station afeedback report that includes the feedback codebook.

The transmitter 740 may transmit signals generated by other componentsof the device 705. In some examples, the transmitter 740 may becollocated with a receiver 710 in a transceiver module. For example, thetransmitter 740 may be an example of aspects of the transceiver 920described with reference to FIG. 9 . The transmitter 740 may utilize asingle antenna or a set of antennas.

FIG. 8 shows a block diagram 800 of a communications manager 805 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. The communicationsmanager 805 may be an example of aspects of a communications manager615, a communications manager 715, or a communications manager 910described herein. The communications manager 805 may include ascheduling manager 810, an applied repetition factor manager 815, afeedback codebook manager 820, a feedback report manager 825, aconfigured repetition factor manager 830, a set repetition factormanager 835, a dropped transmission manager 840, and a slot offsetmanager 845. Each of these modules may communicate, directly orindirectly, with one another (e.g., via one or more buses).

The scheduling manager 810 may determine that a base station hasscheduled the UE for one or more downlink transmissions, each of the oneor more downlink transmissions having an associated repetition factorthat corresponds to one of a set of configured repetition factorsconfigured at the UE.

The scheduling manager 810 may receive a configuration of a plurality ofSPS configurations, wherein each downlink transmission of the one ormore downlink transmissions is associated with a common SPSconfiguration or with different SPS configurations of the plurality ofSPS configurations

The applied repetition factor manager 815 may identify an appliedrepetition factor to apply to feedback codebook generation for the oneor more downlink transmissions.

The feedback codebook manager 820 may generate a feedback codebook forreporting feedback for the one or more downlink transmissions, thefeedback codebook populated based on the applied repetition factor andon whether the one or more downlink transmissions were successfullyreceived and decoded.

In some cases, the feedback codebook is generated without respect to adownlink control information associated with the one or more downlinktransmissions.

The feedback report manager 825 may transmit to the base station afeedback report that includes the feedback codebook.

The configured repetition factor manager 830 may identify the appliedrepetition factor based on a maximum number of configured repetitionfactors from the set of configured repetition factors. In some examples,the configured repetition factor manager 830 may identify the maximumnumber of configured repetition factors without counting configuredrepetition factors corresponding to inactive SPS configurations. In someexamples, the configured repetition factor manager 830 may identify themaximum number of configured repetition factors by counting configuredrepetition factors corresponding to both active and inactive SPSconfigurations. The set repetition factor manager 835 may identify theapplied repetition factor as one. In some examples, the set repetitionfactor manager 835 may generate the feedback codebook based on a lastinstance of each downlink transmission that was actually received anddecoded.

The dropped transmission manager 840 may determine, for each of the oneor more downlink transmissions, that one or more instances of thedownlink transmission has been dropped. In some examples, the droppedtransmission manager 840 may generate the feedback codebook differentlyfor the one or more instances of the downlink transmission that has beendropped and for one or more instances of the downlink transmission thatare not dropped. In some examples, the dropped transmission manager 840may generate an ACK/NACK indication for each downlink transmission thatwas actually received and decoded. In some examples, the droppedtransmission manager 840 may refrain from generating an ACK/NACKindication for each instance of a dropped downlink transmissionopportunity.

The slot offset manager 845 may generate the feedback codebook based onevaluating each of the set of reporting offset values within theevaluation window.

In some cases, the feedback codebook is a type-1 codebook.

FIG. 9 shows a diagram of a system 900 including a device 905 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. The device 905 maybe an example of or include the components of device 605, device 705, ora UE 115 as described herein. The device 905 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including a communicationsmanager 910, an I/O controller 915, a transceiver 920, an antenna 925,memory 930, and a processor 940. These components may be in electroniccommunication via one or more buses (e.g., bus 945).

The communications manager 910 may determine that a base station hasscheduled the UE for one or more downlink transmissions, each of the oneor more downlink transmissions having an associated repetition factorthat corresponds to one of a set of configured repetition factorsconfigured at the UE, identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions,generate a feedback codebook for reporting feedback for the one or moredownlink transmissions, the feedback codebook populated based on theapplied repetition factor and on whether the one or more downlinktransmissions were successfully received and decoded, and transmit tothe base station a feedback report that includes the feedback codebook.

The I/O controller 915 may manage input and output signals for thedevice 905. The I/O controller 915 may also manage peripherals notintegrated into the device 905. In some cases, the I/O controller 915may represent a physical connection or port to an external peripheral.In some cases, the I/O controller 915 may utilize an operating systemsuch as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, oranother known operating system. In other cases, the I/O controller 915may represent or interact with a modem, a keyboard, a mouse, atouchscreen, or a similar device. In some cases, the I/O controller 915may be implemented as part of a processor. In some cases, a user mayinteract with the device 905 via the I/O controller 915 or via hardwarecomponents controlled by the I/O controller 915.

The transceiver 920 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 920 may represent a wireless transceiver and may communicatebi-directionally with another wireless transceiver. The transceiver 920may also include a modem to modulate the packets and provide themodulated packets to the antennas for transmission, and to demodulatepackets received from the antennas.

In some cases, the wireless device may include a single antenna 925.However, in some cases the device may have more than one antenna 925,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 930 may include random access memory (RAM) and read-onlymemory (ROM). The memory 930 may store computer-readable,computer-executable code 935 including instructions that, when executed,cause the processor to perform various functions described herein. Insome cases, the memory 930 may contain, among other things, a BIOS whichmay control basic hardware or software operation such as the interactionwith peripheral components or devices.

The processor 940 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 940 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into the processor 940. The processor 940 may beconfigured to execute computer-readable instructions stored in a memory(e.g., the memory 930) to cause the device 905 to perform variousfunctions (e.g., functions or tasks supporting type-1 codebookconstruction with multiple aggregation factors).

The code 935 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 935 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 935 may not be directly executable by theprocessor 940 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 10 shows a block diagram 1000 of a device 1005 that supports type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure. The device 1005 may be anexample of aspects of a base station 105 as described herein. The device1005 may include a receiver 1010, a communications manager 1015, and atransmitter 1020. The device 1005 may also include a processor. Each ofthese components may be in communication with one another (e.g., via oneor more buses).

The receiver 1010 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to type-1codebook construction with multiple aggregation factors, etc.).Information may be passed on to other components of the device 1005. Thereceiver 1010 may be an example of aspects of the transceiver 1320described with reference to FIG. 13 . The receiver 1010 may utilize asingle antenna or a set of antennas.

The communications manager 1015 may schedule a UE for one or moredownlink transmissions, each of the one or more downlink transmissionshaving an associated repetition factor that corresponds to one of a setof configured repetition factors configured at the UE, identify anapplied repetition factor for the UE to apply to feedback codebookgeneration for the one or more downlink transmissions, and receive afeedback report from the UE that includes a feedback codebook, thefeedback codebook generated for reporting feedback for the one or moredownlink transmissions and populated based on the applied repetitionfactor and on whether the one or more downlink transmissions weresuccessfully received and decoded by the UE. The communications manager1015 may be an example of aspects of the communications manager 1310described herein.

The communications manager 1015, or its sub-components, may beimplemented in hardware, code (e.g., software or firmware) executed by aprocessor, or any combination thereof. If implemented in code executedby a processor, the functions of the communications manager 1015, or itssub-components may be executed by a general-purpose processor, a DSP, anASIC, a FPGA or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described in the presentdisclosure.

The communications manager 1015, or its sub-components, may bephysically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations by one or more physical components. In some examples, thecommunications manager 1015, or its sub-components, may be a separateand distinct component in accordance with various aspects of the presentdisclosure. In some examples, the communications manager 1015, or itssub-components, may be combined with one or more other hardwarecomponents, including but not limited to an I/O component, atransceiver, a network server, another computing device, one or moreother components described in the present disclosure, or a combinationthereof in accordance with various aspects of the present disclosure.

The transmitter 1020 may transmit signals generated by other componentsof the device 1005. In some examples, the transmitter 1020 may becollocated with a receiver 1010 in a transceiver module. For example,the transmitter 1020 may be an example of aspects of the transceiver1320 described with reference to FIG. 13 . The transmitter 1020 mayutilize a single antenna or a set of antennas.

FIG. 11 shows a block diagram 1100 of a device 1105 that supports type-1codebook construction with multiple aggregation factors in accordancewith aspects of the present disclosure. The device 1105 may be anexample of aspects of a device 1005, or a base station 105 as describedherein. The device 1105 may include a receiver 1110, a communicationsmanager 1115, and a transmitter 1135. The device 1105 may also include aprocessor. Each of these components may be in communication with oneanother (e.g., via one or more buses).

The receiver 1110 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to type-1codebook construction with multiple aggregation factors, etc.).Information may be passed on to other components of the device 1105. Thereceiver 1110 may be an example of aspects of the transceiver 1320described with reference to FIG. 13 . The receiver 1110 may utilize asingle antenna or a set of antennas.

The communications manager 1115 may be an example of aspects of thecommunications manager 1015 as described herein. The communicationsmanager 1115 may include a scheduling manager 1120, an appliedrepetition factor manager 1125, and a feedback report manager 1130. Thecommunications manager 1115 may be an example of aspects of thecommunications manager 1310 described herein.

The scheduling manager 1120 may schedule a UE for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a set ofconfigured repetition factors configured at the UE.

The applied repetition factor manager 1125 may identify an appliedrepetition factor for the UE to apply to feedback codebook generationfor the one or more downlink transmissions.

The feedback report manager 1130 may receive a feedback report from theUE that includes a feedback codebook, the feedback codebook generatedfor reporting feedback for the one or more downlink transmissions andpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded bythe UE.

The transmitter 1135 may transmit signals generated by other componentsof the device 1105. In some examples, the transmitter 1135 may becollocated with a receiver 1110 in a transceiver module. For example,the transmitter 1135 may be an example of aspects of the transceiver1320 described with reference to FIG. 13 . The transmitter 1135 mayutilize a single antenna or a set of antennas.

FIG. 12 shows a block diagram 1200 of a communications manager 1205 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. The communicationsmanager 1205 may be an example of aspects of a communications manager1015, a communications manager 1115, or a communications manager 1310described herein. The communications manager 1205 may include ascheduling manager 1210, an applied repetition factor manager 1215, afeedback report manager 1220, a configured repetition factor manager1225, a set repetition factor manager 1230, a dropped transmissionmanager 1235, and a feedback codebook manager 1240. Each of thesemodules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

The scheduling manager 1210 may schedule a UE for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a set ofconfigured repetition factors configured at the UE.

The scheduling manager 1210 may transmit a configuration of a pluralityof SPS configurations, wherein each downlink transmission of the one ormore downlink transmissions is associated with a common SPSconfiguration or with different SPS configurations of the plurality ofSPS configurations.

The applied repetition factor manager 1215 may identify an appliedrepetition factor for the UE to apply to feedback codebook generationfor the one or more downlink transmissions.

The feedback report manager 1220 may receive a feedback report from theUE that includes a feedback codebook, the feedback codebook generatedfor reporting feedback for the one or more downlink transmissions andpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded bythe UE.

The configured repetition factor manager 1225 may identify the appliedrepetition factor based on a maximum number of configured repetitionfactors from the set of configured repetition factors. In some examples,the configured repetition factor manager 1225 may identify the maximumnumber of configured repetition factors without counting configuredrepetition factors corresponding to inactive SPS configurations of theUE. In some examples, the configured repetition factor manager 1225 mayidentify the maximum number of configured repetition factors by countingconfigured repetition factors corresponding to both active and inactiveSPS configurations of the UE.

The set repetition factor manager 1230 may identify the appliedrepetition factor as one, where the feedback codebook is generated basedon a last instance of each downlink transmission that was actuallyreceived and decoded. In some examples, the set repetition factormanager 1230 may schedule, based on the set of configured repetitionfactors, at least one non-conflicted instance of the downlinktransmission during an evaluation window that is based on a reportingoffset value.

The dropped transmission manager 1235 may determine, for each of the oneor more downlink transmissions, that one or more instances of thedownlink transmission has been dropped, where the feedback codebook isgenerated differently for the one or more instances of the downlinktransmission that has been dropped and for one or more instances of thedownlink transmission that are not dropped. In some cases, the feedbackcodebook is generated based on, an ACK/NACK indication is generated foreach downlink transmission that was actually received and decoded by theUE, and an ACK/NACK indication is not generated for each instance of adropped downlink transmission opportunity.

The feedback codebook manager 1240 may monitor, control, or otherwisemanage aspects of the feedback codebook being generated without respectto a downlink control information associated with the one or moredownlink transmissions. In some cases, the UE is configured with a setof reporting offset values for transmitting the feedback report to thebase station, each of the set of reporting offset values representing anumber of slots after a last nominal downlink transmission, the set ofreporting offset values spanning an evaluation window, and the feedbackcodebook is generated based on the UE evaluating each of the set ofreporting offset values within the evaluation window.

In some cases, the feedback codebook is a type-1 codebook.

FIG. 13 shows a diagram of a system 1300 including a device 1305 thatsupports type-1 codebook construction with multiple aggregation factorsin accordance with aspects of the present disclosure. The device 1305may be an example of or include the components of device 1005, device1105, or a base station 105 as described herein. The device 1305 mayinclude components for bi-directional voice and data communicationsincluding components for transmitting and receiving communications,including a communications manager 1310, a network communicationsmanager 1315, a transceiver 1320, an antenna 1325, memory 1330, aprocessor 1340, and an inter-station communications manager 1345. Thesecomponents may be in electronic communication via one or more buses(e.g., bus 1350).

The communications manager 1310 may schedule a UE for one or moredownlink transmissions, each of the one or more downlink transmissionshaving an associated repetition factor that corresponds to one of a setof configured repetition factors configured at the UE, identify anapplied repetition factor for the UE to apply to feedback codebookgeneration for the one or more downlink transmissions, and receive afeedback report from the UE that includes a feedback codebook, thefeedback codebook generated for reporting feedback for the one or moredownlink transmissions and populated based on the applied repetitionfactor and on whether the one or more downlink transmissions weresuccessfully received and decoded by the UE.

The network communications manager 1315 may manage communications withthe core network (e.g., via one or more wired backhaul links). Forexample, the network communications manager 1315 may manage the transferof data communications for client devices, such as one or more UEs 115.

The transceiver 1320 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1320 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1320 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1325.However, in some cases the device may have more than one antenna 1325,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 1330 may include RAM, ROM, or a combination thereof. Thememory 1330 may store computer-readable code 1335 including instructionsthat, when executed by a processor (e.g., the processor 1340) cause thedevice to perform various functions described herein. In some cases, thememory 1330 may contain, among other things, a basic input/output system(BIOS) which may control basic hardware or software operation such asthe interaction with peripheral components or devices.

The processor 1340 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1340 may be configured to operate a memoryarray using a memory controller. In some cases, a memory controller maybe integrated into processor 1340. The processor 1340 may be configuredto execute computer-readable instructions stored in a memory (e.g., thememory 1330) to cause the device 1305 to perform various functions(e.g., functions or tasks supporting type-1 codebook construction withmultiple aggregation factors).

The inter-station communications manager 1345 may manage communicationswith other base station 105, and may include a controller or schedulerfor controlling communications with UEs 115 in cooperation with otherbase stations 105. For example, the inter-station communications manager1345 may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, the inter-station communications manager1345 may provide an X2 interface within an LTE/LTE-A wirelesscommunication network technology to provide communication between basestations 105.

The code 1335 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 1335 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 1335 may not be directly executable by theprocessor 1340 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 14 shows a flowchart illustrating a method 1400 that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure. The operations ofmethod 1400 may be implemented by a UE 115 or its components asdescribed herein. For example, the operations of method 1400 may beperformed by a communications manager as described with reference toFIGS. 6 through 9 . In some examples, a UE may execute a set ofinstructions to control the functional elements of the UE to perform thefunctions described below. Additionally or alternatively, a UE mayperform aspects of the functions described below using special-purposehardware.

At 1405, the UE may determine that a base station has scheduled the UEfor one or more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a set of configured repetition factors configured at the UE. Theoperations of 1405 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1405 may beperformed by a scheduling manager as described with reference to FIGS. 6through 9 .

At 1410, the UE may identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions.The operations of 1410 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1410may be performed by an applied repetition factor manager as describedwith reference to FIGS. 6 through 9 .

At 1415, the UE may generate a feedback codebook for reporting feedbackfor the one or more downlink transmissions, the feedback codebookpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded.The operations of 1415 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1415may be performed by a feedback codebook manager as described withreference to FIGS. 6 through 9 .

At 1420, the UE may transmit to the base station a feedback report thatincludes the feedback codebook. The operations of 1420 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1420 may be performed by a feedback report manager asdescribed with reference to FIGS. 6 through 9 .

FIG. 15 shows a flowchart illustrating a method 1500 that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure. The operations ofmethod 1500 may be implemented by a UE 115 or its components asdescribed herein. For example, the operations of method 1500 may beperformed by a communications manager as described with reference toFIGS. 6 through 9 . In some examples, a UE may execute a set ofinstructions to control the functional elements of the UE to perform thefunctions described below. Additionally or alternatively, a UE mayperform aspects of the functions described below using special-purposehardware.

At 1505, the UE may determine that a base station has scheduled the UEfor one or more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a set of configured repetition factors configured at the UE. Theoperations of 1505 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1505 may beperformed by a scheduling manager as described with reference to FIGS. 6through 9 .

At 1510, the UE may identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions.The operations of 1510 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1510may be performed by an applied repetition factor manager as describedwith reference to FIGS. 6 through 9 .

At 1515, the UE may identify the applied repetition factor based on amaximum number of configured repetition factors from the set ofconfigured repetition factors. The operations of 1515 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1515 may be performed by a configured repetitionfactor manager as described with reference to FIGS. 6 through 9 .

At 1520, the UE may generate a feedback codebook for reporting feedbackfor the one or more downlink transmissions, the feedback codebookpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded.The operations of 1520 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1520may be performed by a feedback codebook manager as described withreference to FIGS. 6 through 9 .

At 1525, the UE may transmit to the base station a feedback report thatincludes the feedback codebook. The operations of 1525 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1525 may be performed by a feedback report manager asdescribed with reference to FIGS. 6 through 9 .

FIG. 16 shows a flowchart illustrating a method 1600 that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure. The operations ofmethod 1600 may be implemented by a UE 115 or its components asdescribed herein. For example, the operations of method 1600 may beperformed by a communications manager as described with reference toFIGS. 6 through 9 . In some examples, a UE may execute a set ofinstructions to control the functional elements of the UE to perform thefunctions described below. Additionally or alternatively, a UE mayperform aspects of the functions described below using special-purposehardware.

At 1605, the UE may determine that a base station has scheduled the UEfor one or more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a set of configured repetition factors configured at the UE. Theoperations of 1605 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1605 may beperformed by a scheduling manager as described with reference to FIGS. 6through 9 .

At 1610, the UE may identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions.The operations of 1610 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1610may be performed by an applied repetition factor manager as describedwith reference to FIGS. 6 through 9 .

At 1615, the UE may identify the applied repetition factor as one. Theoperations of 1615 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1615 may beperformed by a set repetition factor manager as described with referenceto FIGS. 6 through 9 .

At 1620, the UE may generate a feedback codebook for reporting feedbackfor the one or more downlink transmissions, the feedback codebookpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded.The operations of 1620 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1620may be performed by a feedback codebook manager as described withreference to FIGS. 6 through 9 .

At 1625, the UE may generate the feedback codebook based on a lastinstance of each downlink transmission that was actually received anddecoded. The operations of 1625 may be performed according to themethods described herein. In some examples, aspects of the operations of1625 may be performed by a set repetition factor manager as describedwith reference to FIGS. 6 through 9 .

At 1630, the UE may transmit to the base station a feedback report thatincludes the feedback codebook. The operations of 1630 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1630 may be performed by a feedback report manager asdescribed with reference to FIGS. 6 through 9 .

FIG. 17 shows a flowchart illustrating a method 1700 that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure. The operations ofmethod 1700 may be implemented by a base station 105 or its componentsas described herein. For example, the operations of method 1700 may beperformed by a communications manager as described with reference toFIGS. 10 through 13 . In some examples, a base station may execute a setof instructions to control the functional elements of the base stationto perform the functions described below. Additionally or alternatively,a base station may perform aspects of the functions described belowusing special-purpose hardware.

At 1705, the base station may schedule a UE for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a set ofconfigured repetition factors configured at the UE. The operations of1705 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1705 may be performed by ascheduling manager as described with reference to FIGS. 10 through 13 .

At 1710, the base station may identify an applied repetition factor forthe UE to apply to feedback codebook generation for the one or moredownlink transmissions. The operations of 1710 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1710 may be performed by an applied repetition factormanager as described with reference to FIGS. 10 through 13 .

At 1715, the base station may receive a feedback report from the UE thatincludes a feedback codebook, the feedback codebook generated forreporting feedback for the one or more downlink transmissions andpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded bythe UE. The operations of 1715 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1715may be performed by a feedback report manager as described withreference to FIGS. 10 through 13 .

FIG. 18 shows a flowchart illustrating a method 1800 that supportstype-1 codebook construction with multiple aggregation factors inaccordance with aspects of the present disclosure. The operations ofmethod 1800 may be implemented by a base station 105 or its componentsas described herein. For example, the operations of method 1800 may beperformed by a communications manager as described with reference toFIGS. 10 through 13 . In some examples, a base station may execute a setof instructions to control the functional elements of the base stationto perform the functions described below. Additionally or alternatively,a base station may perform aspects of the functions described belowusing special-purpose hardware.

At 1805, the base station may schedule a UE for one or more downlinktransmissions, each of the one or more downlink transmissions having anassociated repetition factor that corresponds to one of a set ofconfigured repetition factors configured at the UE. The operations of1805 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1805 may be performed by ascheduling manager as described with reference to FIGS. 10 through 13 .

At 1810, the base station may identify an applied repetition factor forthe UE to apply to feedback codebook generation for the one or moredownlink transmissions. The operations of 1810 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1810 may be performed by an applied repetition factormanager as described with reference to FIGS. 10 through 13 .

At 1815, the base station may receive a feedback report from the UE thatincludes a feedback codebook, the feedback codebook generated forreporting feedback for the one or more downlink transmissions andpopulated based on the applied repetition factor and on whether the oneor more downlink transmissions were successfully received and decoded bythe UE. The operations of 1815 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1815may be performed by a feedback report manager as described withreference to FIGS. 10 through 13 .

At 1820, the base station may determine, for each of the one or moredownlink transmissions, that one or more instances of the downlinktransmission has been dropped, where the feedback codebook is generateddifferently for the one or more instances of the downlink transmissionthat has been dropped and for one or more instances of the downlinktransmission that are not dropped. The operations of 1820 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1820 may be performed by a droppedtransmission manager as described with reference to FIGS. 10 through 13.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at a UE, comprising:determining that a base station has scheduled the UE for one or moredownlink transmissions, each of the one or more downlink transmissionshaving an associated repetition factor that corresponds to one of aplurality of configured repetition factors configured at the UE;identifying an applied repetition factor to apply to feedback codebookgeneration for the one or more downlink transmissions; generating afeedback codebook for reporting feedback for the one or more downlinktransmissions, the feedback codebook populated based at least in part onthe applied repetition factor and on whether the one or more downlinktransmissions were successfully received and decoded; and transmittingto the base station a feedback report that includes the feedbackcodebook.

Aspect 2: The method of aspect 1, further comprising: identifying theapplied repetition factor based at least in part on a maximum number ofconfigured repetition factors from the plurality of configuredrepetition factors.

Aspect 3: The method of aspect 2, further comprising: identifying themaximum number of configured repetition factors without countingconfigured repetition factors corresponding to inactive SPSconfigurations.

Aspect 4: The method of any of aspects 2 through 3, further comprising:identifying the maximum number of configured repetition factors bycounting configured repetition factors corresponding to both active andinactive SPS configurations.

Aspect 5: The method of any of aspects 1 through 4, further comprising:identifying the applied repetition factor as one; and generating thefeedback codebook based at least in part on a last instance of eachdownlink transmission that was actually received and decoded.

Aspect 6: The method of any of aspects 1 through 5, further comprising:determining, for each of the one or more downlink transmissions, thatone or more instances of the downlink transmission has been dropped; andgenerating the feedback codebook differently for the one or moreinstances of the downlink transmission that has been dropped and for oneor more instances of the downlink transmission that are not dropped.

Aspect 7: The method of aspect 6, wherein generating the feedbackcodebook further comprises: generating an ACK/NACK indication for eachdownlink transmission that was actually received and decoded; andrefraining from generating an ACK/NACK indication for each instance of adropped downlink transmission opportunity.

Aspect 8: The method of any of aspects 1 through 7, further comprising:receiving a configuration of a plurality of SPS configurations, whereineach downlink transmission of the one or more downlink transmissions isassociated with a common SPS configuration or with different SPSconfigurations of the plurality of SPS configurations.

Aspect 9: The method of any of aspects 1 through 8, wherein the feedbackcodebook is generated without respect to a DCI associated with the oneor more downlink transmissions.

Aspect 10: The method of any of aspects 1 through 9, wherein the UE isconfigured with a plurality of reporting offset values for transmittingthe feedback report to the base station, each of the plurality ofreporting offset values representing a number of slots after a lastnominal downlink transmission, the plurality of reporting offset valuesspanning an evaluation window, the method further comprising: generatingthe feedback codebook based at least in part on evaluating each of theplurality of reporting offset values within the evaluation window.

Aspect 11: The method of any of aspects 1 through 10, wherein thefeedback codebook comprises a type-1 codebook.

Aspect 12: A method for wireless communication at a base station,comprising: scheduling a UE for one or more downlink transmissions, eachof the one or more downlink transmissions having an associatedrepetition factor that corresponds to one of a plurality of configuredrepetition factors configured at the UE; identifying an appliedrepetition factor for the UE to apply to feedback codebook generationfor the one or more downlink transmissions; and receiving a feedbackreport from the UE that includes a feedback codebook, the feedbackcodebook generated for reporting feedback for the one or more downlinktransmissions and populated based at least in part on the appliedrepetition factor and on whether the one or more downlink transmissionswere successfully received and decoded by the UE.

Aspect 13: The method of aspect 12, further comprising: identifying theapplied repetition factor based at least in part on a maximum number ofconfigured repetition factors from the plurality of configuredrepetition factors.

Aspect 14: The method of aspect 13, further comprising: identifying themaximum number of configured repetition factors without countingconfigured repetition factors corresponding to inactive SPSconfigurations of the UE.

Aspect 15: The method of any of aspects 13 through 14, furthercomprising: identifying the maximum number of configured repetitionfactors by counting configured repetition factors corresponding to bothactive and inactive SPS configurations of the UE.

Aspect 16: The method of any of aspects 12 through 15, furthercomprising: identifying the applied repetition factor as one, whereinthe feedback codebook is generated based at least in part on a lastinstance of each downlink transmission that was actually received anddecoded.

Aspect 17: The method of aspect 16, further comprising: scheduling,based at least in part on the plurality of configured repetitionfactors, at least one non-conflicted instance of the downlinktransmission during an evaluation window that is based at least in parton a reporting offset value.

Aspect 18: The method of any of aspects 12 through 17, furthercomprising: determining, for each of the one or more downlinktransmissions, that one or more instances of the downlink transmissionhas been dropped, wherein the feedback codebook is generated differentlyfor the one or more instances of the downlink transmission that has beendropped and for one or more instances of the downlink transmission thatare not dropped.

Aspect 19: The method of aspect 18, wherein the feedback codebook isgenerated based at least in part on, an ACK/NACK indication is generatedfor each downlink transmission that was actually received and decoded bythe UE, and an ACK/NACK indication is not generated for each instance ofa dropped downlink transmission opportunity.

Aspect 20: The method of any of aspects 12 through 19, furthercomprising: transmitting a configuration of a plurality of SPSconfigurations, wherein each downlink transmission of the one or moredownlink transmissions is associated with a common SPS configuration orwith different SPS configurations of the plurality of SPSconfigurations.

Aspect 21: The method of any of aspects 12 through 20, wherein thefeedback codebook is generated without respect to a DCI associated withthe one or more downlink transmissions.

Aspect 22: The method of any of aspects 12 through 21, wherein the UE isconfigured with a plurality of reporting offset values for transmittingthe feedback report to the base station, each of the plurality ofreporting offset values representing a number of slots after a lastnominal downlink transmission, the plurality of reporting offset valuesspanning an evaluation window, and the feedback codebook is generatedbased at least in part on the UE evaluating each of the plurality ofreporting offset values within the evaluation window.

Aspect 23: The method of any of aspects 12 through 22, wherein thefeedback codebook comprises a type-1 codebook.

Aspect 24: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 1 through 11.

Aspect 25: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 1 through11.

Aspect 26: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 1through 11.

Aspect 27: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 12 through 23.

Aspect 28: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects12 through 23.

Aspect 29: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 12 through 23.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may bedescribed for purposes of example, and LTE, LTE-A, LTE-A Pro, or NRterminology may be used in much of the description, the techniquesdescribed herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NRnetworks. For example, the described techniques may be applicable tovarious other wireless communication systems such as Ultra MobileBroadband (UMB), Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, aswell as other systems and radio technologies not explicitly mentionedherein.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, a CPU, an FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices (e.g., acombination of a DSP and a microprocessor, multiple microprocessors, oneor more microprocessors in conjunction with a DSP core, or any othersuch configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein may be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that may beaccessed by a general-purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude random-access memory (RAM), read-only memory (ROM), electricallyerasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other non-transitory medium that may be used tocarry or store desired program code means in the form of instructions ordata structures and that may be accessed by a general-purpose orspecial-purpose computer, or a general-purpose or special-purposeprocessor. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition ofcomputer-readable medium. Disk and disc, as used herein, include CD,laser disc, optical disc, digital versatile disc (DVD), floppy disk andBlu-ray disc where disks usually reproduce data magnetically, whilediscs reproduce data optically with lasers. Combinations of the aboveare also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an example step that is described as “based on condition A”may be based on both a condition A and a condition B without departingfrom the scope of the present disclosure. In other words, as usedherein, the phrase “based on” shall be construed in the same manner asthe phrase “based at least in part on.”

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “example” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, known structures and devices are shown inblock diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person having ordinaryskill in the art to make or use the disclosure. Various modifications tothe disclosure will be apparent to a person having ordinary skill in theart, and the generic principles defined herein may be applied to othervariations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described herein,but is to be accorded the broadest scope consistent with the principlesand novel features disclosed herein.

1. A method for wireless communication at a user equipment (UE),comprising: determining that a network device has scheduled the UE forone or more downlink transmissions, each of the one or more downlinktransmissions having an associated repetition factor that corresponds toone of a plurality of configured repetition factors configured at theUE; identifying an applied repetition factor to apply to feedbackcodebook generation for the one or more downlink transmissions;generating a feedback codebook for reporting feedback for the one ormore downlink transmissions, the feedback codebook populated based atleast in part on the applied repetition factor; and transmitting to thenetwork device a feedback report that includes the feedback codebook. 2.The method of claim 1, further comprising: identifying the appliedrepetition factor based at least in part on a maximum number ofconfigured repetition factors from the plurality of configuredrepetition factors.
 3. The method of claim 2, further comprising:identifying the maximum number of configured repetition factors withoutcounting configured repetition factors corresponding to inactivesemi-persistent scheduling (SPS) configurations.
 4. The method of claim2, further comprising: identifying the maximum number of configuredrepetition factors by counting configured repetition factorscorresponding to both active and inactive semi-persistent scheduling(SPS) configurations.
 5. The method of claim 1, further comprising:identifying the applied repetition factor as one; and generating thefeedback codebook.
 6. The method of claim 1, further comprising:determining, for each of the one or more downlink transmissions, thatone or more instances of the downlink transmission has been dropped; andgenerating the feedback codebook differently for the one or moreinstances of the downlink transmission that has been dropped and for oneor more instances of the downlink transmission that are not dropped. 7.The method of claim 6, wherein generating the feedback codebook furthercomprises: generating an acknowledgement/negative-acknowledgement(ACK/NACK) indication for each downlink transmission that was actuallyreceived and decoded; and refraining from generating an ACK/NACKindication for each instance of a dropped downlink transmissionopportunity.
 8. The method of claim 1, further comprising: receiving aconfiguration of a plurality of semi-persistent scheduling (SPS)configurations, wherein each downlink transmission of the one or moredownlink transmissions is associated with a common SPS configuration orwith different SPS configurations of the plurality of SPSconfigurations.
 9. The method of claim 1, wherein the feedback codebookis generated without respect to a downlink control informationassociated with the one or more downlink transmissions.
 10. The methodof claim 1, wherein the UE is configured with a plurality of reportingoffset values for transmitting the feedback report to the networkdevice, each of the plurality of reporting offset values representing anumber of slots after a last nominal downlink transmission, theplurality of reporting offset values spanning an evaluation window, themethod further comprising: generating the feedback codebook based atleast in part on evaluating each of the plurality of reporting offsetvalues within the evaluation window.
 11. The method of claim 1, whereinthe feedback codebook comprises a type-1 codebook.
 12. A method forwireless communication at a network device, comprising: scheduling auser equipment (UE) for one or more downlink transmissions, each of theone or more downlink transmissions having an associated repetitionfactor that corresponds to one of a plurality of configured repetitionfactors configured at the UE; identifying an applied repetition factorfor the UE to apply to feedback codebook generation for the one or moredownlink transmissions; and receiving a feedback report from the UE thatincludes a feedback codebook, the feedback codebook generated forreporting feedback for the one or more downlink transmissions andpopulated based at least in part on the applied repetition factor. 13.The method of claim 12, further comprising: identifying the appliedrepetition factor based at least in part on a maximum number ofconfigured repetition factors from the plurality of configuredrepetition factors.
 14. The method of claim 13, further comprising:identifying the maximum number of configured repetition factors withoutcounting configured repetition factors corresponding to inactivesemi-persistent scheduling (SPS) configurations of the UE.
 15. Themethod of claim 13, further comprising: identifying the maximum numberof configured repetition factors by counting configured repetitionfactors corresponding to both active and inactive semi-persistentscheduling (SPS) configurations of the UE.
 16. The method of claim 12,further comprising: identifying the applied repetition factor as one.17. The method of claim 16, further comprising: scheduling, based atleast in part on the plurality of configured repetition factors, atleast one non-conflicted instance of the downlink transmission during anevaluation window that is based at least in part on a reporting offsetvalue.
 18. The method of claim 12, further comprising: determining, foreach of the one or more downlink transmissions, that one or moreinstances of the downlink transmission has been dropped, wherein thefeedback codebook is generated differently for the one or more instancesof the downlink transmission that has been dropped and for one or moreinstances of the downlink transmission that are not dropped.
 19. Themethod of claim 18, wherein the feedback codebook is generated based atleast in part on, an acknowledgement/negative-acknowledgement (ACK/NACK)indication is generated for each downlink transmission that was actuallyreceived and decoded by the UE, and an ACK/NACK indication is notgenerated for each instance of a dropped downlink transmissionopportunity.
 20. An apparatus for wireless communication at a userequipment (UE), comprising: a processor, memory coupled with theprocessor; and instructions stored in the memory and executable by theprocessor to cause the apparatus to: determine that a network device hasscheduled the UE for one or more downlink transmissions, each of the oneor more downlink transmissions having an associated repetition factorthat corresponds to one of a plurality of configured repetition factorsconfigured at the UE; identify an applied repetition factor to apply tofeedback codebook generation for the one or more downlink transmissions;generate a feedback codebook for reporting feedback for the one or moredownlink transmissions, the feedback codebook populated based at leastin part on the applied repetition factor; and transmit to the networkdevice a feedback report that includes the feedback codebook.
 21. Theapparatus of claim 20, wherein the instructions are further executableby the processor to cause the apparatus to: identify the appliedrepetition factor as one; and generate the feedback codebook.
 22. Theapparatus of claim 20, wherein the instructions are further executableby the processor to cause the apparatus to: determine, for each of theone or more downlink transmissions, that one or more instances of thedownlink transmission has been dropped; and generate the feedbackcodebook differently for the one or more instances of the downlinktransmission that has been dropped and for one or more instances of thedownlink transmission that are not dropped.
 23. The apparatus of claim22, wherein the instructions to generate the feedback codebook furtherare executable by the processor to cause the apparatus to: generate anacknowledgement/negative-acknowledgement (ACK/NACK) indication for eachdownlink transmission that was actually received and decoded; andrefrain from generating an ACK/NACK indication for each instance of adropped downlink transmission opportunity.
 24. The apparatus of claim20, wherein the instructions are further executable by the processor tocause the apparatus to: receive a configuration of a plurality ofsemi-persistent scheduling (SPS) configurations, wherein each downlinktransmission of the one or more downlink transmissions is associatedwith a common SPS configuration or with different SPS configurations ofthe plurality of SPS configurations.
 25. The apparatus of claim 20,wherein the feedback codebook is generated without respect to a downlinkcontrol information associated with the one or more downlinktransmissions.
 26. The apparatus of claim 20, wherein the UE isconfigured with a plurality of reporting offset values for transmittingthe feedback report to the network device, each of the plurality ofreporting offset values representing a number of slots after a lastnominal downlink transmission, the plurality of reporting offset valuesspanning an evaluation window.
 27. The apparatus of claim 20, whereinthe feedback codebook comprises a type-1 codebook.
 28. The apparatus ofclaim 20, wherein the instructions are further executable by theprocessor to cause the apparatus to: identify the applied repetitionfactor as one.
 29. An apparatus for wireless communication at a networkdevice, comprising: a processor, memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to: schedule a user equipment (UE) for one or moredownlink transmissions, each of the one or more downlink transmissionshaving an associated repetition factor that corresponds to one of aplurality of configured repetition factors configured at the UE;identify an applied repetition factor for the UE to apply to feedbackcodebook generation for the one or more downlink transmissions, theapplied repetition factor being different from the associated repetitionfactor of the one or more downlink transmissions; and receive a feedbackreport from the UE that includes a feedback codebook, the feedbackcodebook generated for reporting feedback for the one or more downlinktransmissions and populated based at least in part on the appliedrepetition factor.
 30. The apparatus of claim 20, wherein theinstructions are further executable by the processor to cause theapparatus to: identify the applied repetition factor as one.